Methods and systems for analyzing accessing of drug dispensing systems

ABSTRACT

Various aspects described herein relate to presenting drug dispensing information. Data related to a plurality of dispensing events initiated by one or more employees, of an electronic drug dispensing system can be received. A set of dispensing events of the plurality of dispensing events can be determined as constituting possible misappropriation of drugs by the one or more employees. An alert related to the set of dispensing events can be provided based on determining that the set of dispensing events constitute possible misappropriation of drugs.

CLAIM OF PRIORITY UNDER 35 U.S.C. § 119

This application is a continuation of and claims the benefit of priorityto U.S. Non-Provisional application Ser. No. 17/669,855, filed on Feb.11, 2022, which claims the benefit of priority to U.S. Non-Provisionalapplication Ser. No. 16/436,643, filed Jun. 10, 2019, now U.S. Pat. No.11,282,597, issued Mar. 22, 2022, which is a continuation-in-part ofU.S. Non-Provisional application Ser. No. 15/078,736, filed Mar. 23,2016, now U.S. Pat. No. 10,679,737, issued Jun. 9, 2020, which claimsthe benefit of priority to U.S. Provisional Application No. 62/139,494,filed Mar. 27, 2015, all of which are incorporated herein by referencein their entireties.

BACKGROUND

With the advent of electronic medical records, a patient's medicalrecord can be accessible by various employees operating in a healthcareprovider network. The nature of medical workflows is such thattraditional role- or attribute-based access control for the medicalrecords may not be feasible as the complexity of clinical care mayresult in various parties needing to access a patient's medical record,and indeed, rigid access controls may prevent access in emergencysituations. Accordingly, however, a given patient's medical record maybe subject to breach, or inappropriate accessing, by various parties. Amultitude of scenarios for breach can be envisioned where an employeemay access a medical record of someone with whom they have a personalinterest (e.g., a celebrity, family member, co-worker, etc.) who may beunder the care of the healthcare provider network, where the access isunrelated to the employee actually providing services to that person inthe healthcare industry. Not only is inappropriate accessing generallynot desirable, but it can also result in fines to the healthcareprovider network. Accordingly, it is in the healthcare providernetwork's interest to prevent inappropriate accessing of electronicmedical records. Moreover, patients who feel their medical records arebeing compromised are much less likely to divulge truthful medicalinformation to the healthcare provider network, and thus patient caremay be impacted in this regard.

Auditing systems have been developed for tracking employee access ofmedical records, but these systems do not provide certain desirableanalyses of the accessing.

In addition, electronic medical records can be used to operate orauthorize operation of electronic drug dispensing systems. For example,electronic drug dispensing systems can be deployed at medical centers(e.g., on hospital floors, doctor's offices, etc.), and medical centerpersonnel can operate the electronic drug dispensing systems to dispensecertain drugs for certain patients. The electronic drug dispensingsystems may dispense drugs for an identified patient based on a doctor'sorder accessed from an electronic medical record, and may log what drugsare dispensed for the patient, the quantity of drugs dispensed, thetime/date of dispensing, etc.

The medical center personnel typically handle the drugs from theelectronic drug dispensing system to the patient's location. Inaddition, in some cases, the medical center personnel may “waste” drugs,which can refer to a process of accounting for unused or mishandleddrugs, that are to be disposed of. This process of “wasting” typicallyrequires a witness to sign or acknowledge the “wasting.” There are manypoints of potential misappropriation of drugs obtained from electronicdrug dispensing systems.

Auditing systems have been developed for tracking drugs dispensed viadrug dispensing systems, but these systems do not provide certaindesirable analyses of the use and/or disposition of the dispensed drugs.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

In accordance with an aspect described herein a method for presentingelectronic patient data accessing information is provided. The methodincludes receiving data related to a plurality of access events, by oneor more employees, of electronic patient data, determining a set ofaccess events in the plurality of access events constitute, by the oneor more employees, possible breach of the electronic patient data, andproviding an alert related to the set of access events based ondetermining that the set of access events constitute possible breach ofthe electronic patient data.

In another aspect, an apparatus for presenting electronic patient dataaccessing information. The apparatus includes at least one processorconfigured to perform various operations. The at least one processor canbe configured to receive data related to a plurality of access events,by one or more employees, of electronic patient data, determine a set ofaccess events of the plurality of access events constitute, by the oneor more employees, possible breach of the electronic patient data, andprovide an alert related to the set of access events based ondetermining that the set of access events constitute possible breach ofthe electronic patient data. The apparatus also includes a memorycoupled to the at least one processor.

In yet another aspect, a non-transitory computer-readable medium storingcomputer executable code for presenting electronic patient dataaccessing information is provided. The code includes code for receivingdata related to a plurality of access events, by one or more employees,of electronic patient data, determining a set of access events of theplurality of access events constitute, by the one or more employees,possible breach of the electronic patient data, and providing an alertrelated to the set of access events based on determining that the set ofaccess events constitute possible breach of the electronic patient data.

In another aspect, a method for presenting drug dispensing informationis provided. The method includes receiving data related to a pluralityof dispensing events initiated by one or more employees, of anelectronic drug dispensing system, determining a set of dispensingevents in the plurality of dispensing events that constitute possiblemisappropriation of drugs from the electronic drug dispensing system bythe one or more employees, and providing an alert related to the set ofdispensing events based on determining that the set of dispensing eventsconstitute the possible misappropriation of drugs.

In another aspect, an apparatus for presenting drug dispensinginformation includes at least one processor and a memory coupled to theat least one processor. The at least one processor is configured toreceive data related to a plurality of dispensing events initiated byone or more employees, of an electronic drug dispensing system,determine a set of dispensing events in the plurality of dispensingevents constitute possible misappropriation of drugs from the electronicdrug dispensing system by the one or more employees, and provide analert related to the set of dispensing events based on determining thatthe set of dispensing events constitute the possible misappropriation ofdrugs.

In another example, a non-transitory computer-readable medium storingcomputer executable code for presenting drug dispensing information isprovided. The code includes code for receiving data related to aplurality of dispensing events initiated by one or more employees, of anelectronic drug dispensing system, determining a set of dispensingevents in the plurality of dispensing events constitute possiblemisappropriation of drugs from the electronic drug dispensing system bythe one or more employees, and providing an alert related to the set ofdispensing events based on determining that the set of dispensing eventsconstitute the possible misappropriation of drugs.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction withthe appended drawings, provided to illustrate and not to limit thedisclosed aspects, wherein like designations denote like elements.

FIG. 1 illustrates an example system for presenting electronic patientdata access data in accordance with aspects described herein.

FIG. 2 illustrates an example method for presenting electronic patientdata access data in accordance with aspects described herein.

FIG. 3 illustrates an example method for presenting electronic patientdata access data in accordance with aspects described herein.

FIGS. 4-7 illustrate example graphical user interface (GUI) screens inaccordance with aspects described herein.

FIG. 8 illustrates example rules, tags, or meta data in accordance withaspects described herein.

FIG. 9 illustrates an example method for presenting drug dispensing datain accordance with aspects described herein.

FIGS. 10-14 illustrate additional example graphical user interface (GUI)screens in accordance with aspects described herein.

FIG. 15 is an example system architecture in accordance with aspectsdescribed herein.

FIG. 16 is an example system diagram of various hardware components andother features, for use in accordance with aspects described herein.

FIG. 17 is a block diagram of various example system components, for usein accordance with aspects described herein.

DETAILED DESCRIPTION

Aspects described herein generally relate to collecting data from one ormore entities in a healthcare provider network, and analyzing the datato determine possible inappropriate accessing of the data ormisappropriation of drugs. For example, determining the possibleinappropriate accessing (also referred to herein as “breach”) of thedata or misappropriation of drugs can be a manual or automated processbased on other analysis of the data. For example, the collected data caninclude electronic patient data (e.g., from an electronic medical record(EMR)) and data related to accessing the electronic patient data (e.g.,an identifier of an employee accessing the EMR data, a time of accessingthe EMR data, etc.), data from an electronic drug dispensing system(e.g., dispensing data such as time of dispensing, amount of dispensing,type of drug dispensed, wasting activity, etc.). The data may alsoinclude human resources (HR) data that can indicate information relatedto the employees accessing the electronic patient data and/or dispensingthe drugs. The collected data can be analyzed, as described herein, todetect whether one or more accesses of the data may possibly be a breachof the data, whether one or more dispensing of drugs is possibly forinappropriate purposes, etc. If possible breach or misappropriation isdetected, one or more alerts can be generated (e.g., to one or moreinterfaces) for further investigation as to whether theaccess/dispensing is inappropriate given additional context around theaccess/dispensing. In another example, a representation of the collecteddata can be generated based on the analysis and provided to an interfaceto facilitate breach/misappropriation detection. Moreover, though EMRdata is generally referred to herein, the concepts described can beapplied to substantially any electronically stored patient data.

In one specific example, data received from the various sources can beanalyzed based on rule-based analysis. In additional examples, the datacan be analyzed based on one or more of clusterings of data (e.g., basedon one or more determined relationships), machine-learning related tothe data, network or other statistics analysis (e.g., Markov chains),etc. In this regard, in an example, one or more ontologies relating tothe data can be generated to correlate the data such to enrich eventsbeing tracked with clinical context. For example, accesses of similarelectronic patient data by different employees can be observed over time(e.g., based on statistical analysis) such to associate the differentemployees as part of a clinical care team. In this regard, in oneexample, access of a related EMR by an employee outside of the clinicalcare team may indicate a possible breach in accessing the EMR.Similarly, access of an EMR by an employee on the clinical care teamwithout similar accessing by other members of the clinical care team mayindicate possible breach in accessing the EMR. These example analysescombine and either add to or detract, with unequal weights, from thesuspicious nature of event, and increase or decrease the probabilitythat such events are a breach. In any case, when parameters from thedata related to an access event achieve a threshold for possible breach,an alert can be generated for providing to an interface for managingcompliance for further investigation. In addition, in an example,feedback regarding alerts can be received and utilized in determiningthresholds for subsequent alerts such to allow for more or lessconservative breach detection.

It is to be appreciated that each healthcare provider network and/or arelated entity (e.g., hospital, doctor's office, etc.) may have adifferent workflow, and thus the analysis of the data in this regardfacilitates providing customized breach detection for a given workflow.In a specific example, a hospital may employ a nurse anesthetist in theOperating Room who records the initiation of surgery, while anotherhospital might employ anesthesiologists who records the initiation ofanesthesia. Additionally, in another specific example, some physiciansmay use phone or email to follow up with patients after an appointmentand thus access patient data between appointments where other physiciansmight only access patient data while the patient is in clinic. Moreover,in another specific example, some clinics may use nurses in anadministrative role (such as office assistant) whereas other clinicsmight use nurses in a research capacity similar to an academicphysician, etc. In any case, analyzing the data using clustering,machine-learning, network or other statistical analysis, etc. allows forbreach detection for a given workflow than more rigid strictlyrule-based systems.

In another specific example, where data received from various sources isanalyzed based on rule-based analysis, accesses of an electronic drugdispensing system by different employees can be observed over time(e.g., based on statistical analysis) to detect potentialmisappropriation of drugs from the electronic drug dispensing system.For example, log files from the electronic drug dispensing system may beanalyzed to determine dispensing behavior, wasting behavior, etc.Certain types of drugs can trigger alerts for certain behavior. In otherexamples, statistical analysis can allow for discovering frequentwasting of certain specific drugs, types of drugs, etc. by an employee,by a department or team, etc. In any case, when parameters from the datarelated to an access event or multiple access events achieve a thresholdfor possible breach, an alert can be generated for providing to aninterface for managing drug misappropriation for further investigation.In addition, in an example, feedback regarding alerts can be receivedand utilized in determining thresholds for subsequent alerts such toallow for more or less conservative misappropriation detection.

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details.

As used herein, the term “determining” or “evaluating” encompasses awide variety of actions. For example, “determining” and “evaluating” mayinclude calculating, computing, processing, deriving, investigating,looking up (e.g., looking up in a table, a database or other datarepository, or another data structure), ascertaining, and/or the like.Also, “determining,” and “evaluating” may include receiving (e.g.,receiving information), accessing (e.g., accessing data in a datarepository), and/or the like. Also, “determining” may include resolving,selecting, choosing, establishing, and the like.

As used herein, the terms “element,” “module,” “component,” and “system”may refer to a computer-related entity, either hardware, a combinationof hardware and software, software, or software in execution. Forexample, a module may be, but is not limited to being, amachine-executable process running on a processor, a processor, anobject, a thread of execution, a machine-executable program, and/or acomputer. By way of illustration, both a process running on a server andthe server may be a module or a component. One or more modules orcomponents may reside within a process and/or thread of execution. Insome implementations, a module may be localized on one computer and/ordistributed among two or more computers.

It will be appreciated that, in accordance with one or more aspectsdescribed herein, inferences may be made regarding determining protocolsto provide to the application, analyzing data for performance of theprotocols, and/or the like, as described. As used herein, the term to“infer” or “inference” refers generally to the process of reasoningabout or inferring states of the system, environment, and/or user from aset of observations as captured via events and/or data. Inference may beemployed to identify a specific context or action, or may generate aprobability distribution over states, for example. The inference may beprobabilistic—that is, the computation of a probability distributionover states of interest based on a consideration of data and events.Inference may also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether or not the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources.

Various aspects or features will be presented herein in terms of systemsthat may include a number of devices, components, modules, and the like.It is to be understood and appreciated that the various systems mayinclude additional devices, components, modules, etc. and/or may notinclude all of the devices, components, modules, etc., discussed inconnection with the figures. A combination of these approaches may alsobe used.

Referring to FIGS. 1-3 and 9 , aspects are depicted with reference toone or more components and one or more methods that may perform theactions or functions described herein. Although the operations describedbelow in FIGS. 2-3 and 9 are presented in a particular order and/or asbeing performed by an example component, it should be understood thatthe ordering of the actions and the components performing the actionsmay be varied, depending on the implementation. Moreover, it should beunderstood that the following actions or functions may be performed by aspecially-programmed processor, a processor executingspecially-programmed software or computer-readable media, or by anyother combination of a hardware component and/or a software componentcapable of performing the described actions or functions.

Referring to FIG. 1 , an example system 100 is illustrated thatfacilitates processing EMR access data to determine one or more possiblebreaches of EMR data and/or processing drug dispensing data to determineone or more possible misappropriations of drugs. System 100 includes ahealthcare provider network platform 102 for storing and facilitatingviewing, modifying, etc. EMRs relating to one or more patients currentlyor previously in (or scheduled for) care of a healthcare providernetwork (e.g., hospital, doctor's office, imaging center, laboratory,etc.) related to the healthcare provider network platform 102.Healthcare provider network platform 102 can communicate over a network104 (e.g., a local area network (LAN), Internet, etc.) with one or moreother nodes, such as device 106, to allow accessing of the healthcareprovider network platform 102 to view one or more EMRs, analyzeaccessing of EMRs, etc.

Healthcare provider network platform 102 includes EMR data 120 (and/ormore generally electronic patient data), which may include a pluralityof EMRs and/or other data related to a plurality of patients. The EMRdata 120 can indicate demographic information regarding a patient (e.g.,name, address, phone number, gender, date of birth, etc.) as well asmedical history information regarding the patient (e.g., symptoms,diagnoses, allergies, conditions, etc.). The medical history informationcan relate to current or previous (or scheduled) care with thehealthcare provider network. EMRs can be stored electronically such tofacilitate electronic access thereto for viewing, modifying, etc. theinformation related to a given patient. This can improve convenience ofaccessing the information, but can also present security concernsrelated to accessing the information. For example, as described,restricting access to EMRs for certain employees of the healthcareprovider network can be impractical in a clinical care settingespecially in emergency situations. Thus, various employees of thehealthcare provider network may have unrestricted access to EMRs (or atleast access that errs on the side of more information to account forsituations where more data may be needed to provide adequatehealthcare). This can lend to inappropriate accessing of EMRs such todetermine protected information regarding certain patients. For example,an employee may seek medical history information for a celebrity, familymember, or other person of interest though the access of information maybe unrelated to care of the patient by the employee. Accordingly,healthcare provider network platform 102 can facilitate detection ofvarious possible inappropriate data accesses (e.g., breaches) of the EMRdata 120.

Healthcare provider network platform 102 can also include EMR accessdata 122, which may include one or more access logs that indicate time,type, employee, etc. related to accessing EMR data 120, and humanresources (HR) data 124 for the employees of the healthcare providernetwork that indicate personal information for the employees, such asname, address, phone number, position, department, etc. In an example,the employees of the healthcare provider network may also includecontract employees (e.g., insurance billers), research employees, etc.,that may not necessarily be directly connected to care of a patient. TheEMR data 120, EMR access data 122, and/or HR data 124 may be analyzedtogether to determine possible breaches in accessing the EMR data 120.Moreover, though shown as part of the healthcare provider networkplatform 102, it is to be appreciated that a portion or all of EMR data120, EMR access data 122, and/or HR data 124 can exist in one or moreother platforms or systems, and may be imported to or otherwise accessedby healthcare provider network platform 102 for analyzing EMR accesses.

Healthcare provider network platform 102 can also include a datareceiving component 126 for receiving at least one of the EMR data 120,EMR access data 122, and/or HR data 124, a data analyzing component 128for analyzing the received data to detect one or more possible breachesof the EMR data 120, and a data presenting component 130 for presentingthe analyzed data, the one or more possible breaches, etc. Healthcareprovider network platform 102 may also optionally include a feedbackcomponent 132 for receiving feedback regarding a detected possiblebreach for use by data analyzing component 128 in detecting one or moresubsequent possible breaches of the data. Data analyzing component 128may optionally include a rule applying component 134 for applying one ormore rules to detect a possible breach in the data, and/or a datapatterning component 136 for detecting one or more patterns in the data,which may be used to determine one or more possible breaches in thedata. The various components of the healthcare provider network platformmay be co-located within a system or network, and/or may be distributedamong various systems and/or networks that can communicate with oneanother (e.g., via network 104 or other networks).

In an additional or alternative example, the healthcare provider networkplatform 102 may include or otherwise interface with one or moreelectronic drug dispensing systems 150, which may also be referred to asan automatic dispensing cabinet (ADC). For example, the electronic drugdispensing systems 150 may store drugs for dispensing to patients of thehealthcare provider network (e.g., patients in hospital rooms,out-patients in doctors' offices, etc.). A healthcare professional mayaccess an electronic drug dispensing system 150 to obtain drugsprescribed for a given patient to administer the drugs to that patient.In an example, the electronic drug dispensing system 150 may provide aninterface for the healthcare professional to identify the patient andrequest the drugs listed on the prescription. The electronic drugdispensing system 150 may provide the healthcare professional withaccess to one or more drugs based on a request. In one example, theelectronic drug dispensing system 150 may interface with EMR data 120 oran associated application to obtain or modify patient information,prescription information, patient diagnosis information, etc., which canalso be used in authorizing and/or logging drug dispensing. Moreover, inan example, the electronic drug dispensing system 150 may interface withHR data 124 to obtain healthcare professional employment information,security profiles, etc., which can also be used in authorizing and/orlogging drug dispensing.

The electronic drug dispensing system 150 may include some drug securingfeatures, such as compartments for one or more specific drugs to preventobtaining drugs that are not part of an associated prescription, adispensing feature to control the number of drugs dispensed for a givenrequest (e.g., based on the prescription or otherwise), etc. Moreover,in an example, the electronic drug dispensing system 150 and/orhealthcare provider network platform 102 can provide a process for“wasting” drugs dispensed by the electronic drug dispensing system 150.For example, where drugs are dispensed by not given to the patient(which may be for substantially any reason, such as patient refusal,drug contamination, etc.), electronic drug dispensing system 150 and/orhealthcare provider network platform 102 can allow for creating an eventindicating that the drug was dispensed but not used (and indeed disposedof). The event may also require a witness to approve the event beforethe event is processed. In any case, drug dispensing data 152 can belogged by the electronic drug dispensing system 150 (and/or by thehealthcare provider network platform 102) to include drug dispensinginformation (e.g., a healthcare professional requesting dispensing,prescription/patient information, drug being dispensed, amountdispensed, wasting information, etc.).

In this regard, data receiving component 126 can also receive the drugdispensing data 152, and data analyzing component 129 can analyze thedrug dispensing data to detect possible misappropriation of drugs. Forexample, rule applying component 134 can apply one or more rules to thedrug dispensing data 152 to detect possible misappropriation, datapatterning component 136 can determine one or more patterns ofdispensing and/or detect outlier dispensing activity, etc. Wherepossible misappropriation is detected, data presenting component 130 canpresent an alert on the interface to allow further investigation (e.g.,within the drug dispensing data 152 or other offline investigation). Inaddition, in an example, feedback component 132 can allow for specifyingvalidity of a detected misappropriation for refining futuremisappropriation detection processes.

FIG. 2 illustrates an example method 200 for processing electronicpatient data access data to determine possible breaches in accessingEMRs. Method 200 includes, at Block 202, receiving data related to aplurality of access events of electronic patient data by one or moreemployees. Data receiving component 126 can receive data related to theplurality of access events of electronic patient data by one or moreemployees. This can optionally include, at Block 204, receiving datafrom EMR access logs, EMRs, and human resources data. Thus, for example,data receiving component 126 can receive data from EMR access logs(e.g., EMR access data 122), EMRs (e.g., EMR data 120), and humanresources data (e.g., HR data 124). As described, data receivingcomponent 126 may receive this data from one or more data sources in ahealthcare provider network and/or other system or network, which may bedistributed across one or more networks, co-located, etc.

Method 200 also includes, at Block 206, determining at least one accessevent of the plurality of access events by the one or more employeesthat constitute possible breach of the electronic patient data. Dataanalyzing component 128 can determine the plurality of access events bythe one or more employees that constitute possible breach of theelectronic patient data. For example, this can optionally include, atBlock 208, detecting the at least one access event based on one or morerules. Data analyzing component 128 may include rule applying component134 for detecting the at least one access event based on the one or morerules. In one example, rule applying component 134 can apply one or morerules to the data using a rules-based mechanism to determine the atleast one access event constituting the possible breach. For instance,the one or more rules may relate to detecting common data among EMRaccess data 122 and HR data 124. In a specific example, rules applyingcomponent 134 may apply one or more rules to the EMR access data 122relating to determining whether an employee accessing an EMR has similarpersonal information as a patient to which the EMR corresponds based onadditionally acquiring EMR data 120 and HR data 124 (e.g., similar lastnames, addresses, phone numbers, etc.). In one example, rule applyingcomponent 134 may additionally apply filtering rules in this example, toprevent excessive false positives (e.g., for common last names). In anycase, in this example, data analyzing component 128 may determine apossible breach in the electronic patient data, which may be presentedto an interface as described herein for further investigation.

In another example, the one or more rules may relate to determiningwhether data relating to a position of the employee from HR data 124(e.g., or inferred through other data, such as determining a syntheticdepartment of the employee as described further below) corresponds tocare of the patient based on the EMR data 120. For instance, the one ormore rules may relate to determining whether a pediatric employee (e.g.,physician, nurse, administrative assistant, etc.) accesses an EMR of anolder patient (e.g., based on an age of the patient according to the EMRdata 120), as this may constitute a possible breach in accessing the EMRdata 120. For example, one or more such rules may be based on a positionand/or department (e.g., rules may be present for administrativeassistants, but perhaps not for doctors, and/or may relate to whetherpatient care based on the EMR data 120 corresponds to a department ofthe employee based on HR data 124). Thus, in one example, a cardiologyadministrative assistant accessing a patient EMR with no cardiac symptomor condition history may result in detecting a possible breach in thedata. In an example, rule applying component 134 may apply multiplerules in detecting a possible breach (e.g., similar last name betweenemployee and patient along with the fact that the employee has notprovided care to the patient based on the EMR data 120).

It is to be appreciated that rule applying component 134 may apply theone or more rules to filter the data for possible breaches, and thepossible breaches may further be analyzed based on patterning, asdescribed below, and/or the data may be analyzed based instead onpatterning without applying the one or more rules described above. Inanother example, the one or more rules may relate to the patterned data,and thus rule applying component 134 may apply one or more rules topatterned data determined by data patterning component 136 to detectpossible breach.

In any case, determining the at least one access event that constitutepossible breach of the electronic patient data may additionally oralternatively optionally include, at Block 210, detecting one or morepatterns of accessing the electronic patient data by one or moreemployees based on the plurality of access events. Data analyzingcomponent 128 may include data patterning component 136 for detectingone or more patterns of accessing the electronic patient data by one ormore employees based on the plurality of access events. For example,data patterning component 136 may detect the one or more patterns atleast in part by clustering the data related to accessing of theelectronic patient data based on detecting commonalities in the data,machine-learning commonalities in the data, network analyzingcommonalities in the data (e.g., generating Markov chains), etc. Thecommonalities can be determined based on computing statisticalinferences such that data commonalities are meaningful. For instance,data patterning component 136 may detect patterns by a given employee(e.g., typical EMR accessing times by the employee), patterns for groupsof employees (e.g., determining that a group of employees typicallyaccess the same medical record, which may be in a given order orotherwise), etc. In an example, in this regard, data analyzing component128 may determine the at least one access that constitute possiblebreach of the electronic patient data based at least in part ondetecting that the at least one access is inconsistent with the one ormore patterns determined by the data patterning component 136.

In a specific example, data patterning component 136 may detect, basedon the EMR access data 122, that an employee typically accesses EMRs inthe EMR data 120 very quickly (e.g., opens access and closes access ofthe EMR within 1 minute). Accordingly, data analyzing component 128 maydetermine whether EMR access data 122 includes one or more accesses bythe employee that achieve a threshold duration over the normal (orcomputed average) for the employee, which may indicate a possible breachin accessing the EMR data 120 by the employee (e.g., when analyzed withother patterns and/or rules applied to the data). In another specificexample, data patterning component 136 may detect that accesses by theemployee according to the EMR access data 122 typically occur at a givenworkstation in the healthcare provider network (e.g., based on anidentifier, network address, etc. related to the workstation), and dataanalyzing component 128 may determine whether the EMR access data 122includes one or more accesses by the employees from a differentworkstation, which may indicate a possible breach.

In another specific example, data patterning component 136 may generateone or more patterns regarding employee transitions between EMR accessesfor one or more patients (e.g., in one or more departments, etc.). Inthis example, data analyzing component 128 may detect transitions fromone EMR access action to another in a given department (e.g., an officeassistant who frequently schedules patients moving to an action ofadding information to a patient's EMR) that are of low probability givenan individually fit gamma distribution for the employee, that aredetected to be outside of a defined number of standard deviations beyonda mean value for the employee, etc. For example, it is to be appreciatedthat the number of standard deviations may be specified by anadministrator or other user account of the healthcare provider networkplatform 102 (e.g., per a given employee, group or type of employees,all employees, etc.) or otherwise configured to achieve a desired levelof possible breach detection. More generally, data patterning component136 can generate fingerprints of detected behavior patterns for one ormore employees based on analyzing the EMR access data 122 in thisregard, and data analyzing component 128 can determine EMR accesses thatare outside of the fingerprints. For example, data patterning component136 can generate fingerprints based at least in part on mathematicallyrepresenting and characterizing the EMR access data for the givenemployee to detect typical patternable EMR access behavior by theemployee. In addition, in an example similar to the rules-based exampledescribed above for an employee accessing an EMR for a patient relatedto a department (or having a condition relating to a department)inconsistent with the employee's department, it may be possible that theemployee accesses such EMRs outside of the department regularly as partof her/his employment. Thus, in an example, data patterning component136 may additionally or alternatively determine that an employeetypically accesses EMRs corresponding to one or more departments (e.g.,regardless of a department for the employee in HR data 124), and dataanalyzing component 128 may detect a possible breach where the employeeaccesses EMR(s) outside of the detected one or more departments forwhich the employee typically accesses EMRs.

In another specific example, data patterning component 136 may detectaccessing of certain EMRs in the EMR data 120 by a group of employeesbased on the EMR access data 122. For example, data patterning component136 may determine that a certain one or more doctors, assistants,nurses, administrative assistants, etc. typically access the same EMRs,which may indicate these employees as part of a clinical care group.Accordingly, data analyzing component 128 may determine whether EMRaccess data 122 indicates accesses to EMRs by a portion of the employeesin the group but not by another portion, which may indicate a possiblebreach. For example, this may be based on a time of the accessingaccording to the EMR access data 122, such that an access by a portionof the employees in a group that is not within a threshold time ofaccess by the other portion of the employees in the group may indicate apossible breach. In another example, data analyzing component 128 maydetermine whether EMR access data 122 indicates accesses to an EMR bythe group and a corresponding access to the EMR by another employee thatis not in the group, which may indicate a possible breach.

It is to be appreciated that data patterning component 136 canconstantly or periodically generate the one or more patterns such thatthe patterns can evolve over time based on changes to other data in thehealthcare provider network platform 102 (e.g., addition, movement,removal, etc. of employees in the EMR access data 122 and/or HR data124, etc.). Moreover, for example, EMR access data 122 can beperiodically received in EMR data logs, received using a request/receivemechanism (e.g., file transfer protocol (FTP)), publish/subscribemechanism, etc.).

Method 200 also includes, at Block 212, providing an alert related tothe at least one access event based on determining that the at least oneaccess event constitutes possible breach of the electronic patient data.Data presenting component 130 can provide the alert related to the atleast one access event based on determining that the at least one accesseven constitutes possible breach of the electronic patient data. Forexample, data presenting component 130 can render the alert on aninterface (e.g., a dashboard interface of alerts, a patient profileinterface graphically depicting EMR access data 122 related to accessingthe EMR, etc.), as described further herein. The alert may allow aprofessional to receive the alert and further investigate the alert todetermine whether a possible breach of the data has occurred and/or toremediate the possible breach. In an example, the further investigationcan be facilitated by indications on interfaces presented by the datapresenting component 130 that relate to rules of rule applying component134, data patterns from data patterning component 136, etc. as describedfurther herein.

In addition, in an example, data analyzing component 128 may determine aconfidence level or priority related to a detected possible breach,which may be based on which of the one or more rules the detectedpossible breach satisfies, which of the one or more patterns to whichthe detected possible breach relates, a level of deviation from the oneor more patterns, and/or the like. In this example, data presentingcomponent 130 may provide a representation of the access event alongwith any confidence or priority information.

Method 200 may optionally include, at Block 214, employing feedbackreceived related to determining the at least one access eventconstitutes possible breach of the electronic patient data indetermining whether one or more subsequent access events constitutepossible breach of the electronic patient data. For example, feedbackcomponent 132 can receive and employ feedback related to determining theat least one access event constitutes possible breach of the electronicpatient data in determining whether one or more subsequent access eventsconstitute possible breach of the electronic patient data. In anexample, feedback can be provided via one or more interfaces to indicatewhether a possible breach detection is actually considered a breach,whether breach detection is too conservative, and/or whether moreconservative breach detection is desired. Data analyzing component 128can utilize the feedback information to automaticallyactivate/deactivate one or more rules used by rule applying component134, one or more patterns detected in the EMR access data 122 by datapatterning component 136, one or more numbers of standard deviations fordetecting possible breaches, etc. to achieve a desired level ofconsideration for determining whether accesses defined in the EMR accessdata 122 are possible breach of the EMR data 120.

FIG. 3 illustrates an example method 300 for processing EMR access datato determine possible breaches in accessing EMRs. Method 300 includes,at Block 202, receiving data related to a plurality of access events ofelectronic patient data by one or more employees. Data receivingcomponent 126 can receive data related to the plurality of access eventsof electronic patient data by one or more employees, as described. Thiscan optionally include, at Block 204, receiving data from EMR accesslogs, EMRs, and human resources data. Thus, for example, data receivingcomponent 126 can receive data from EMR access logs (e.g., EMR accessdata 122), EMRs (e.g., EMR data 120), and human resources data (e.g., HRdata 124). As described, data receiving component 126 may receive thisdata from one or more data sources in a healthcare provider networkand/or other system or network, which may be distributed across one ormore networks, co-located, etc.

Method 300 also optionally includes, at Block 302, filtering theelectronic patient data based on one or more whitelist events. Forexample, data analyzing component 128 can filter the electronic patientdata based on the one or more whitelist events. This may includefiltering out the whitelist events as accesses to EMR data 120 (e.g.,from the EMR access data 122) that are determined to not constitute apossible breach (e.g., legitimate authorized accesses of the EMR data120). For example, data analyzing component 128 can determine thewhitelist events from EMR access data 122 as accesses that demonstratethe employee has directly treated a patient corresponding to the EMRdata being accessed and/or have contributed to their care. For example,whitelist events may include appointment entry, an entry related toordering a procedure or medication for the patient, an update to allergyinformation, a patient check-in, a modification to primary careprovider, etc. Thus, for example, accessing of EMR data in EMR accessdata 122 around these whitelist events may be filtered out. For example,this may lessen processing burden for determining possible breaches fromthe EMR access data 122, as described further below, as statisticalprocessing, pattern detection, etc. can occur on a subset of the entireEMR access data 122 having filtered out the whitelist events. Anon-exhaustive list of example whitelist events (which can also bereferred to as “positive tags”) that can be detected by data analyzingcomponent 128 in the EMR access data 122 (e.g., by determining a type ofthe EMR access as specified in or otherwise determined based on the EMRaccess data 122) is provided below.

This employee entered allergy information for this patient. Thisemployee initiated an admission, discharge or transfer action for thispatient. This employee edited this patient's diagnoses. This employeemodified identity information in this patient's record. This employeeentered immunization information in this patient's record. This employeereviewed and accepted this patient's medication history. This employeecreated an order for this patient. This employee discontinued an orderfor this patient. This employee approved a medication order for thispatient. This employee is the overall care provider. This employeecreated a Procedure note for this patient. This employee is atechnologist who fulfilled an order. This employee is involved withRadiology Information Systems. This employee instantiated a procedure.This employee cancelled something in the EMR. This employee editedsomething in the EMR. This employee edited the patient's emergencydepartment disposition. This employee is the patient's primary carephysician (PCP). This employee is labeled as the visit provider ID,indicating they are the attending provider for the patient's visit. Thisemployee closed the patient encounter. This employee created anappointment for this patient. This employee cancelled an appointment forthis patient. This employee checked in the patient to an appointment.This employee created an after visit summary for this patient. Thisemployee created the patient encounter. This employee updated thepatient's allergies. This employee created the user ID for the patient.This employee last reviewed the patient's medications. This employeereviewed the patient's problem list. This employee edited the patient'sdiagnosis history. This employee has sequentially viewed more than onepatient with a similar name - but only explored one record extensively.This employee accessed a patient's record with explicit permission fromthe compliance office. This employee is a supervisor and is connected tothis patient through a whitelisted subordinate. This employee is atrusted user. This employee is authorized to access this patient's data.

Method 300 also optionally includes, at Block 304, constructingfingerprint data for the one or more employees based on the filtereddata. For example, data analyzing component 128 can construct thefingerprint data for the one or more employees based on the filtereddata. For example, data analyzing component 128 may construct thefingerprint data to include, from the EMR access data 122, a collectionlist of daily encounters of one or more employees at the healthcareinstitution, a collection list of accesses of a patient EMR for multipletime periods occurring throughout the day (e.g., each 15 minute periodof the day) or a daily list, a collection list of employee EMR accessesof patient EMRs for multiple time periods occurring throughout the dayor a daily list, a collection list of patient encounters (e.g., allpatient encounters, encounters within a period of time, etc.), acollection list of synthetic department accesses, and/or the like. Forexample, data analyzing component 128 may determine a syntheticdepartment for an employee based at least in part on detecting a type ofEMR data 120 that is most frequently accessed by the employee (e.g.,intensive care unit (ICU), emergency department, etc.). Furtherprocessing can occur on one or more of the fingerprint data collectionsto determine possible breach of the electronic patient data (e.g., EMRdata 120), as described herein.

Method 300 also includes, at Block 306, determining at least one accessevent of the plurality of access events by the one or more employeesthat constitutes possible breach of the electronic patient data. Forexample, data analyzing component 128 may determine the at least oneaccess event of the plurality of access events by the one or moreemployees that constitutes possible breach of the electronic patientdata. For example, data analyzing component 128 may analyze thefingerprint data for a given employee with whitelist events filteredout. As described, determining the at least one access event at Block306 may optionally include, at Block 308, detecting the at least oneaccess event based on one or more rules. For example, rule applyingcomponent 134 can apply one or more rules to the fingerprint data todetermine whether an access is a possible breach, where the one or morerules may correspond to one or more tags defined for identifying in thefingerprint data. The tags, for example, may include negative tags thatare indicative of possible breach and/or neutral tags that may not alonebe indicative of possible breach, but may add information to an accessidentified as possible breach to indicate whether the access is more orless likely a breach of the EMR data 120.

As described herein the one or more rules/tags may include a pluralityof detectable events in the data. A non-exhaustive list of examplerules/tags and relevant determinations made by the data analyzingcomponent 128 to apply the rule/tag to an EMR access in the fingerprintdata is provided below.

Rule/Tag Relevant Determination This employee viewed a record forAnalyze fingerprint data (e.g., patient encounter a patient that hasnever visited the history) to determine if the patient has everhealthcare institution. visited the healthcare institution. Thisemployee viewed a record Analyze the EMR to determine if clinical datawith no clinical data. exists. This employee does not routinelyHierarchical clustering of employees to determine work with otheremployees in this if employee routinely works with other patient’srecord. employees who access this patient’s record. This employee hasnever viewed Analyze fingerprint data to determine this patient’smedical record. employee/patient combination. This employee viewed thisAnalyze fingerprint data (e.g., patient encounter patient’s medicalrecord outside of history) to determine if the EMR access is a anencounter window. threshold of time after a last patient encounter. Thisemployee is not involved in Analyze fingerprint data to determine ifemployee the treatment of this patient. has edited medical record toindicate they are providing direct care for this patient. This employeehas checked two Analyze fingerprint data to determine if two patientswith the same address. patients accessed by the employee have the sameaddress (e.g., where the accesses occur within a threshold period oftime, such as 1 day). This employee shares the same last Analyzefingerprint data (or access logs) to name as this patient. determine ifa patient of an accessed EMR has the same last name as the employee.This employee works in pediatrics Analyze fingerprint data and HR datato and viewed an adult’s record. determine accesses by the employee andthe employee’s department. This employee is listed as an Analyzefingerprint data and EMR data to emergency contact in this patient’sdetermine if a patient of an accessed EMR has an record. emergencycontact with the same name as the employee. This employee works in aAnalyze fingerprint data and HR data to department that is not relatedto determine a history of associated departments of a this patient’scare. patient EMR, and determine whether the employee is in one of thedepartments. This employee viewed a medical Analyze fingerprint data andHR data (or access record of a hospital employee. logs) to determinewhether a patient of an accessed EMR is an employee (e.g. based on name,address, social security number, etc.). This employee accessed thisrecord Analyze fingerprint data to determine normal from a workstationoutside of their workflow pattern of the employee (e.g., during a normalworkflow pattern. time period, as a sequence of accesses of differenttypes and/or from different locations, etc.) to determine if workstationis outside the normal workflow. This employee routinely times-outAnalyze fingerprint data to determine time of sessions on publicworkstations. periods associated with EMR accesses and/or a number ofEMR accesses during which timeout occurred. This employee generated areport Analyze fingerprint data to determine normal outside of theirnormal workflow workflow pattern of the employee (e.g., during apattern. time period, as a sequence of accesses of different typesand/or from different locations, etc.) to determine if a generatedreport is contrary to the normal workflow. This employee saved a reportto a Analyze fingerprint data to determine a save suspicious location ontheir location of a report (e.g., as being in a location computer.related to a personal storage device, such as an external memory card,cloud storage location, etc.). This employee viewed this record Analyzefingerprint data to determine EMR outside of their normal work shift.accesses outside of shift, where the shift can be determined byanalyzing EMR accesses to determine a typical shift and/or HR data thatmay specify/track the shift. This employee downloaded a large Analyzefingerprint data to determine a number amount of patient data. offingerprints over a period of time compared to a threshold, which may bea configured threshold and/or generated based on analyzing fingerprintsto determine typical accesses by the employee over the period of time.This employee printed a large Analyze fingerprint data to determine anumber amount of patient data. of fingerprints related to printing overa period of time compared to a threshold (e.g., a configured orgenerated threshold, as described above). This employee accessed arecord Analyze fingerprint data (or access logs) to for a patient who isdeceased. determine if an access is for an EMR of a deceased patient.This employee is an OB-GYN Analyze fingerprint data, EMR data, and HRdata professional checking a male (or access logs) to determine that thepatient patient. related to the accessed EMR is male, and a departmentof the employee as OB-GYN. This employee accessed a record Analyzefingerprint data, EMR data, and HR data for a patient who lives near theto determine an address of the patient related to employee. the accessedEMR and an address of the employee, and determine whether the addressesare within a threshold proximity. This employee has accessed a Analyzefingerprint data (e.g., a list of patient patient’s record that has beenaccesses) to determine if there are any accesses of dormant for a periodof time. the EMR within the period of time (e.g., 1 year). This employeeaccessed a record Analyze fingerprint data (e.g., patient encounter fora patient that has not had an data) to determine if there are anypatient encounter within a period of time. encounters within the periodof time (e.g., the last 60 days). This employee is registered as AnalyzeHR data to determine if employee “inactive” by the institution.accessing the EMR is “inactive.” This employee is not listed as Analyzefingerprint data and HR data to assigned to one of the departmentsdetermine if employee accessing the EMR is not this patient visited.assigned to a department the patient visited. This employee is a studentwho Analyze fingerprint data and HR data (or access accessed anotherstudent’s patient logs) to determine if the employee is a student data.and if the patient related to the EMR is a student. This employee ischecking their Analyze fingerprint data (and HR data) to own medicalrecord. determine if the employee and the patient related to the EMR arethe same person. This employee checks two patients Analyze fingerprintdata to determine if patients with the exact same full name. related todifferent EMR accesses by the employee (e.g., within a period of time)have the same full name. This patient’s condition is atypical Analyzefingerprint data (e.g., patient encounter for this employee's accesshistory. data) to determine typical access history and conditionsassociated with the patient EMRs to determine if this access is for adifferent condition that is not typically accessed by the employee. Thisemployee created a large Analyze fingerprint data to determine whether anumber of reports on this date. number of reports exceeds a threshold.This employee was logged into Analyze fingerprint data to detectmultiple EMR multiple work stations at this time. accesses inoverlapping periods of time. This employee has sequentially Analyzefingerprint data to detect accessing by viewed more than one patientwith the employee of EMRs of patients having a a similar name - andcontinued to similar name (e.g., same last name) within a explore bothpatients records. period of time of each other. This employee normallyviews a Analyze fingerprint data to determine typical specific age groupthat this patient access history and ages associated with the does notfit into. patient EMRs to determine if this access is for a patient of adifferent age (e.g., exceeding a threshold difference of a typical age).This employee accessed patient Determine VIPs based on searching localor data for a potential VIP. national news feeds, encyclopedia websites,etc. for names and/or events (e.g., that the VIP may be in care of ahealthcare provider), and analyze fingerprint data to detect access ofthe VIP EMR (e.g., based on name/location matching). This employeeaccessed patient Analyze fingerprint data and HR data to data on asubordinate or manager. determine accessing of a patient EMRcorresponding to a subordinate or manager.

Rule applying component 134 can apply one or more of these rules/tags tothe at least one event (e.g., access of an EMR) to determine whether theat least one event is a potential breach of the electronic patient data.For example, data analyzing component 128 can determine whether an eventis a potential breach based on a number of rules/tags that are applied(and/or for which the relevant condition is satisfied), based ondetermining a weighted score of the rules/tags applied to the event,based on determining certain combinations of rules/tags applied to theevent, etc. Moreover, data analyzing component 128 may determine whetheran event is a potential breach based on determining patterns in the dataand detecting deviations from the patterns, etc., as described herein.

As described, determining the at least one access event at Block 306 mayalso optionally include, at Block 310, detecting one or more patterns ofaccessing the electronic patient data by one or more employees based onthe plurality of access events. For example, data patterning component136 may determine the one or more patterns, as described in the rulesabove, such as typical electronic patient data accessing of the employee(e.g., accessing during certain times, accessing EMRs of patients ofcertain ages/diagnoses, etc.). In additional examples, data patterningcomponent 136 may pattern typical accesses from EMR access data 122 forone or more employees based on determining viewing of patients inalphabetical order, determining typical patient identifier patterns usedin accessing the EMR, determining that the employee usually searches bycertain criteria (e.g., name, medical record number (MRN), etc.),determining that the employee normally views old encounters on certaindays of the week, month, etc., determining a certain percentage ofpatients viewed as being male or female, determining a number ofpatients viewed with similar names, etc. In this regard, as described,data patterning component 136 (and/or rule applying component 134) maydetermine whether one or more accesses fall outside of a normaldistribution or standard deviation of the pattern, and may accordinglydetermine at least one access (event) as a possible breach.

Method 300 also includes, at Block 312, providing an alert related tothe at least one access event based on determining that the at least oneaccess event constitutes possible breach of the electronic patient data.Data presenting component 130 can provide the alert related to the atleast one access event based on determining that the at least one accesseven constitutes possible breach of the electronic patient data, asdescribed. For example, data presenting component 130 can render thealert on an interface (e.g., a dashboard interface of alerts, a patientprofile interface graphically depicting EMR access data 122 related toaccessing the EMR, etc.), as described further herein. The alert mayallow a professional to receive the alert and further investigate thealert to determine whether a possible breach of the electronic patientdata has occurred and/or to remediate the possible breach. In anexample, the further investigation can be facilitated by indications oninterfaces presented by the data presenting component 130 that relate torules of rule applying component 134, data patterns from data patterningcomponent 136, etc. as described further herein.

FIGS. 4-7 illustrate example interfaces in accordance with aspectsdescribed herein with respect to implementation of healthcare providernetwork platform 102. In some aspects, the interfaces may includegraphical user interface (GUI) screens configured to interact with oneor more of the various modules/components described herein forproviding/receiving information to/from users. This functionality mayinclude substantially any suitable type of application that sends,retrieves, processes, and/or manipulates input data, receives, displays,formats, and/or communicates output data. For example, such interfacesmay also be associated with an engine, editor tool, web browser, deviceapplication, etc., although other type applications may be utilized. TheGUI may include a display having one or more display objects comprising,e.g., configurable icons, buttons, sliders, input boxes, selectionoptions, menus, tabs having multiple configurable dimensions, shapes,colors, text, data and sounds to facilitate operations with theinterfaces. In addition, among other things, the GUI may also receiveand process user commands from a mouse, touch screen, keyboard, laserpointer, speech input, web site, remote web service and/or other devicessuch as a camera and/or video content, etc. to affect or modifyoperations and/or display of the GUI.

FIG. 4 illustrates an example interface 400 for providing alerts ofpossible breaches in EMR access data. For example, a compliance officeror other administrative user can log into the healthcare providernetwork platform 102 (e.g., via another interface), and can beauthenticated to access the healthcare provider network platform 102,and in particular interface 400, etc. Interface 400 can include a listof one or more alerts 402 generated for possible breaches in EMR accessdata. Interface 400 shows the alerts as separated based on a determinedpriority. In one example, interacting with an alert (e.g., clicking onthe alert) may produce another interface for investigating the alert orrelated information of the associated EMR access event, remediating thepossible breach, indicating whether to present similar indications ofpossible breaches in the future, etc.

FIG. 5 illustrates an example interface 500 for displaying at least aportion of data analysis performed by a healthcare provider networkplatform. For example, interface 500 displays some clustering of data,which can be performed by a data patterning component 136 as describedherein. For example, interface 500 can display a patient summary 502 andemployee information 504 related to an access of the patient's EMR asindicated by EMR access data, as described herein. Accesses of the EMRare indicated by dots 506 over a timeline, where each dot 506corresponds to an access or other action in an EMR of a patient by thelisted employee. In addition, interface 500 can depict groupings 508 ofemployees that are determined to typically access the same EMRs (e.g.within a threshold period of time). For example, one grouping 508 cancorrelate an orthopedic clinic including a registered nurse, aphysician's assistant, and a medical assistant that typically access thesame EMRs (e.g., including the depicted EMR for “Frank McDaniel.” Inthis example interface 500, various groupings of employees associated inclinics are shown as accessing the EMR. A registered nurse that is notpart of the groupings, however, and/or accessed the EMR outside athreshold time within which other employees in the grouping accessed theEMR, is shown as an alert 510 of possible breach of the data (e.g.,based at least on data analyzing component 128 determining that theregistered nurse is not part of the groupings). In addition, interactingwith the alert 510 can cause display of additional information of theEMR access at 512.

FIG. 6 illustrates an example interface 600 for displaying at least aportion of data analysis performed by a healthcare provider networkplatform. For example, interface 600 displays some clustering of data,which can be performed by a data patterning component 136 as describedherein, and in reference to FIG. 5 . In addition, interface 600 caninclude an access of an EMR by office assistance “Rhonda Williams” at602. Interacting with the access 602 on the interface 600, though notindicated as an alert, may cause display of additional informationregarding the access at 604. Displaying the additional information canallow a compliance officer or other administrator to determine whether apossible breach of the data is actually a breach or not.

FIG. 7 illustrates an example interface 700 for displaying EMR accessactivity for a given employee 702. For a given access 704 of an EMR,patient information for the EMR can be displayed at 706 along withadditional information regarding the access at 708. Employee information702 may include access information determined by a data analyzingcomponent 128 as described above, such as average access time, number ofrecords viewed per day, time spent in a current EMR, etc., which canfacilitate determining whether the employee is possibly breaching theEMR data (e.g., where the time spent in the current EMR is determined tobe inconsistent with the average access time).

FIG. 8 illustrates an example of various negative rules/tags 802 for lowlevel alerts that may be applied to electronic patient data, and/oradditional negative rules/tags 804 for determining higher level alerts(e.g., by data analyzing component 128). For example, the negative tags802 for low level alerts may relate to determining an employee checkedan EMR for patients with the same full name (e.g., based on EMR data 120and HR data 124), whether the employee checked an EMR for patients withthe same address as theirs, whether the employee checked patients thatare employed by the same healthcare provider network (e.g., EMR data 120indicates employment and/or patient also located in HR data 124),whether an employee checked an EMR for patients with the same last name,whether a pediatrics employee checked an EMR for patients older than 22(e.g., based on an age/date of birth in the EMR data 120), whether theemployee used a workstation they do not typically use, whether theemployee accessed an unusual encounter department, whether the employeepresented unusual activity for 15 minutes, more generally whetheraccesses of electronic patient data by a given employee fell outside thenormal distribution of behaviors common to employees who are similar inregards to title, department, role, types of patients they encounter,etc., as described above. The EMR access data can be run through one ormore of the negative tags 802 (e.g., as one or more rules presented byrule applying component 134 for determining if the negative tags 802exist in any of the EMR access data 122) to determine whether electronicpatient data accesses satisfy one or more of the negative tags 802, andif so, this can indicate a low level alert of possible data breach.

In addition, other negative tags 804 can be applied to the data forwhich low level alerts are determined to possibly determine higher levelalerts. For example, the other negative tags 804 can relate todetermining if the employee has no previous history of accessing thepatient's EMR, clustering of other employees that have checked thepatient's EMR in common with the employee, and/or determining whetherthe employee and employees are in different clusters (which may indicatecollusion among the employees in breaching the EMR data). This may causegeneration of a higher level (or priority) alert, as described herein.

In a specific example, given two nurses with the same title, jobdescription, role, department, etc., and the fact that they view thesame patient EMRs, or the same type of patient EMRs based on patientdiagnoses, conditions, procedures, or demographics, if accesses by onenurse are detected as different from the other (based on a statisticaldistribution over time, such as increased number of record views perhour, increased time in on patients medical record, access medicalrecords from new workstation, etc.), this behavior may indicate adeviation from the normal, appropriate behavior, and thus a possiblebreach. Accordingly, data analyzing component 128 may detect suchbehavior based on statistical analysis of the EMR access data 122 forthe two nurses (e.g., by data patterning component 136). For example,data analyzing component 128 may evaluate a plurality of the negativetags 802 for low level alerts to detect a concert of multiple deviationsaround a single access event, which may increase the suspicious natureof the access.

In another example, a pediatrician may view patient records with an agedistribution between 0 years old and 21 years old. The EMR access data122 can indicate that one pediatrician views an EMR of a 55 year oldpatient who has never visited that pediatrician's clinic, which isinconsistent with the patient demographic of the pediatrician employee.In addition, to a determination that may relate to detecting thepediatrician accessing an EMR of a 55 year old patient and accessing anEMR of a patient that has not visited the pediatrician's clinic, dataanalyzing component 128 can perform additional non-rule baseddeterminations as well. For instance, data analyzing component 128 candetermine a probability that this patient's medical record is viewed bywhomever the last employee to view it followed by this pediatrician tobe very low (e.g., below a threshold), which may indicate possiblebreach of the data. Similarly, data analyzing component 128 candetermine the fact that this pediatrician preformed one action in thispatient EMR followed by another action to be dissimilar (e.g., outsideof a statistical distribution) to the normal sequence of actions thispediatrician takes when he opens a medical record with patients withsimilar conditions or diagnosis, which can indicate possible breach ofthe data. In either case, for example, data presenting component 130 maypresent an indication of the possible breach on an interface for viewingby a device (e.g., device 106) to analyze, investigate, and/or remediatethe possible breach (e.g., based on other data around the access asdetermined by data analyzing component 128, stored by EMR data 120, EMRaccess data 122, HR data 124, etc., and/or the like).

In another specific example, an insurance/billing specialist accessespatient EMRs at similar rates of progression (e.g., accesses new recordon average of every 50 seconds). Inside every EMR, the billingspecialist may view new procedures accesses that patient's insuranceinformation. While this behavior is not perfectly repetitive, it canfollow a normal distribution of likely sequences of events. If thispattern is disturbed beyond a normal distribution to view a medicalrecord of a patient who is also a fellow employee, this may indicate apossible breach, and data analyzing component 128 may accordingly detectthis disturbing of the pattern beyond a determined normal distributionin EMR access data 122 as a possible breach. For example, it can bedetermined that the billing specialist does not view insuranceinformation (which is consistent with the sequence of events typicallyperformed by the billing specialist), but instead views lab results(which is not consistent with sequence of events typically performed bythe billing specialist), which may indicate possible breach. It is to beappreciated that the deviation in behavior can be detected byautomatically observing baseline normalities (e.g., by a data patterningcomponent 136) and associating the normalities to a curve based onmultiple dimensions (title, department, location, date of hire, etc.).Data analyzing component 128 can then use the normalities to detectdeviation and possible breach (e.g., by a data analyzing component 128),which may be based on a determined degree of deviation.

FIG. 9 illustrates an example method 900 for processing drug dispensingdata to determine possible misappropriation of drugs. Method 900includes, at Block 902, receiving data related to a plurality ofdispensing events of an electronic drug dispensing system by one or moreemployees. Data receiving component 126 can receive data related to theplurality of dispensing events of the electronic drug dispensing systemby one or more employees. This can optionally include, at Block 904,receiving data from dispensing logs, EMRs, and/or human resources data.Thus, for example, data receiving component 126 can receive data as drugdispensing data 152 of the electronic drug dispensing system 150, EMRs(e.g., EMR data 120, which may include prescriptions or otherinformation associated with drugs dispensed or to be dispensed), humanresources data (e.g., HR data 124, which may include employee-relateddata), and/or the like. As described, data receiving component 126 mayreceive this data from one or more data sources including one or moreelectronic drug dispensing systems 150 or a host system to whichmultiple electronic drug dispensing systems 150 connect, a healthcareprovider network and/or other system or network, etc., which may bedistributed across one or more networks, co-located, and/or the like.

Method 900 also includes, at Block 906, determining at least onedispensing event of the plurality of dispensing events by the one ormore employees that constitute possible misappropriation of drugs. Dataanalyzing component 128 can determine the plurality of dispensing eventsby the one or more employees that constitute possible misappropriationof drugs. For example, the plurality of dispensing events may includeevents of actual dispensing requests and/or fulfillment of such requestsby the electronic drug dispensing system 150, created wasting eventswhere drugs dispensed based on a request are wasted, and/or otherinteractions with the electronic drug dispensing system 150 byhealthcare professionals.

In an example, determining the at least one dispensing event at Block906 can optionally include, at Block 908, detecting the at least onedispensing event based on one or more rules. Data analyzing component128 may include rule applying component 134 for detecting the at leastone dispensing event based on the one or more rules. In one example,rule applying component 134 can apply one or more rules to the datausing a rules-based mechanism to determine the at least one dispensingevent constituting the possible misappropriation of drugs. For instance,the one or more rules may relate to detecting dispensing or wasting of acertain drug over a threshold amount over a period of time, by a singlehealthcare professional, by healthcare professionals in the samedepartment or on the same floor (e.g., of a hospital), etc. In onespecific example, all dispensing of a certain drug type (e.g., painkillers) over a threshold quantity (per period of time, per dispensing,etc.) may be detected as a possible misappropriation. In any case, inthis example, data analyzing component 128 may determine a possiblemisappropriation of drugs where one or more rules are satisfied, anindication of which may be presented to an interface as described hereinfor further investigation.

In another example, the one or more rules may relate to determiningwhether data relating to a position of the employee from HR data 124(e.g., or inferred through other data, such as determining a syntheticdepartment of the employee as described further below) corresponds tothe type of drugs and/or quantity of the drugs being dispensed for thepatient. For instance, where different drugs are dispensed (if possiblefrom the electronic drug dispensing system 150) or a higher quantity isdispensed, this may indicate possible misappropriation of drugs. Forexample, one or more such rules may be based on a position and/ordepartment (e.g., rules may be present for physician assistants, nurses,techs, etc., but perhaps not for doctors, and/or may relate to whetherthe type of drug being dispensed corresponds to a department of theemployee based on HR data 124). In an example, rule applying component134 may apply multiple rules in detecting a possible misappropriation ofdrugs (e.g., similar last name between employee and patient along withthe type or quantity of drug dispensed).

It is to be appreciated that rule applying component 134 may apply theone or more rules to filter the data for possible misappropriations, andthe possible misappropriations may further be analyzed based onpatterning, as described below, and/or the data may be analyzed basedinstead on patterning without applying the one or more rules describedabove. In another example, the one or more rules may relate to thepatterned data, and thus rule applying component 134 may apply one ormore rules to patterned data determined by data patterning component 136to detect possible misappropriations of drugs.

In any case, determining the at least one dispensing event thatconstitute possible misappropriation of drugs may additionally oralternatively optionally include, at Block 910, detecting one or morepatterns of dispensing drugs by one or more employees based on theplurality of dispensing events. Data analyzing component 128 may includedata patterning component 136 for detecting one or more patterns ofdispensing the drugs by one or more employees based on the plurality ofdispensing events. For example, data patterning component 136 may detectthe one or more patterns at least in part by clustering the data relatedto dispensing (or wasting) of drugs based on detecting commonalities inthe data, machine-learning commonalities in the data, network analyzingcommonalities in the data (e.g., generating Markov chains), etc. Thecommonalities can be determined based on computing statisticalinferences such that data commonalities are meaningful. For instance,data patterning component 136 may detect patterns by a given employee(e.g., typical drug dispensing times by the employee), patterns forgroups of employees (e.g., determining that a group of employeestypically dispense similar drugs as part of treating patients withsimilar condition), etc. In an example, in this regard, data analyzingcomponent 128 may determine the at least one dispensing event as apattern of dispensing events that may constitute possiblemisappropriation. In another example, data analyzing component 128 maydetermine the at least one dispensing that constitutes possiblemisappropriation of drugs based at least in part on detecting that theat least one dispensing is inconsistent with, or an outlier of, the oneor more patterns determined by the data patterning component 136.

In one specific example, data patterning component 136 may detect apattern of dispensing events that may be indicative of misappropriation,such as wasting of similar drugs over a period of time, wasting of drugsfor the same patient or patients with similar diagnoses or prescriptionsover a period of time, etc. Moreover, in an example, data patterningcomponent 136 may detect the pattern for a single healthcareprofessional dispensing the drugs, professionals that are on the sameteam or same department, professionals that are treating the same orsimilar patients, professionals that are working similar shifts whendispensing/wasting occurs, and/or the like.

In another specific example, data patterning component 136 may detectthat dispensing by the employee typically occur at a given dispenser inthe healthcare provider network (e.g., based on an identifier, networkaddress, etc. related to the dispenser), and data analyzing component128 may determine whether the drug dispensing data 152 includes one ormore dispensings by the employees from a different dispenser, which mayindicate a possible misappropriation (e.g., based additionally on thedrug type, amount, and/or the like).

It is to be appreciated that data patterning component 136 canconstantly or periodically generate the one or more patterns such thatthe patterns can evolve over time based on changes to other data in thehealthcare provider network platform 102 (e.g., addition, movement,removal, etc. of employees in the drug dispensing data 152 and/or HRdata 124, etc.). Moreover, for example, drug dispensing data 152 can beperiodically received in data logs, received using a request/receivemechanism (e.g., file transfer protocol (FTP)), publish/subscribemechanism, etc.).

Method 900 also includes, at Block 912, providing an alert related tothe at least one access event based on determining that the at least oneaccess event constitutes possible breach of the electronic patient data.Data presenting component 130 can provide the alert related to the atleast one access event based on determining that the at least one accesseven constitutes possible breach of the electronic patient data. Forexample, data presenting component 130 can render the alert on aninterface (e.g., a dashboard interface of alerts, a patient profileinterface graphically depicting EMR access data 122 related to accessingthe EMR, etc.), as described further herein. The alert may allow aprofessional to receive the alert and further investigate the alert todetermine whether a possible breach of the data has occurred and/or toremediate the possible breach. In an example, the further investigationcan be facilitated by indications on interfaces presented by the datapresenting component 130 that relate to rules of rule applying component134, data patterns from data patterning component 136, etc. as describedfurther herein.

In addition, in an example, data analyzing component 128 may determine aconfidence level or priority related to a detected possiblemisappropriation, which may be based on which of the one or more rulesthe detected possible misappropriation satisfies, which of the one ormore patterns to which the detected possible misappropriation relates, alevel of deviation from the one or more patterns, and/or the like. Inthis example, data presenting component 130 may provide a representationof the dispensing (or wasting) event along with any confidence orpriority information. Specific examples of interfaces for providing thealerts and/or allowing further investigation are shown herein. Forexample, the alert may also identify the healthcare professionaldispensing the drug, the type and/or amount or drug, a wasting event,prescription information, other dispensing events by the healthcareprofessional or other healthcare professionals that may be related tothe possible misappropriation, etc.

Method 900 may optionally include, at Block 914, employing feedbackreceived related to determining the at least one dispensing eventconstitutes possible misappropriation of drugs in determining whetherone or more subsequent dispensing events constitute possiblemisappropriation of drugs. For example, feedback component 132 canreceive and employ feedback related to determining the at least onedispensing event constitutes possible misappropriation of drugs indetermining whether one or more subsequent dispensing events constitutepossible misappropriation of drugs. In an example, feedback can beprovided via one or more interfaces to indicate whether a possiblemisappropriation detection is actually considered a misappropriation,whether misappropriation detection is too conservative, and/or whethermore conservative misappropriation detection is desired. Data analyzingcomponent 128 can utilize the feedback information to automaticallyactivate/deactivate one or more rules used by rule applying component134, one or more patterns detected in the drug dispensing data 152 bydata patterning component 136, one or more numbers of standarddeviations for detecting possible misappropriation, etc. to achieve adesired level of consideration for determining whether dispensingsdefined in the drug dispensing data 152 indicate possiblemisappropriation of drugs.

FIGS. 10-14 illustrate example interfaces in accordance with aspectsdescribed herein with respect to implementation of healthcare providernetwork platform 102. In some aspects, the interfaces may includegraphical user interface (GUI) screens configured to interact with oneor more of the various modules/components described herein forproviding/receiving information to/from users. This functionality mayinclude substantially any suitable type of application that sends,retrieves, processes, and/or manipulates input data, receives, displays,formats, and/or communicates output data. For example, such interfacesmay also be associated with an engine, editor tool, web browser, deviceapplication, etc., although other type applications may be utilized. TheGUI may include a display having one or more display objects comprising,e.g., configurable icons, buttons, sliders, input boxes, selectionoptions, menus, tabs having multiple configurable dimensions, shapes,colors, text, data and sounds to facilitate operations with theinterfaces. In addition, among other things, the GUI may also receiveand process user commands from a mouse, touch screen, keyboard, laserpointer, speech input, web site, remote web service and/or other devicessuch as a camera and/or video content, etc. to affect or modifyoperations and/or display of the GUI.

FIG. 10 illustrates an example interface 1000 for providing alerts ofpossible misappropriation of drugs (e.g., as detected from drugdispensing data 152). For example, a compliance officer or otheradministrative user can log into the healthcare provider networkplatform 102 (e.g., via another interface), and can be authenticated toaccess the healthcare provider network platform 102, and in particularinterface 1000, etc. Interface 1000 can include a summary 1002 of casesgenerated (e.g., by the data presenting component 130) as possiblemisappropriations of drugs, and another summary 1004 indicating a numberof cases unassigned to administrative personnel, recently modifiedcases, case age, etc. In addition, interface 1000 can include a listing1006 of recent activity of cases that are identified as possiblemisappropriations of drugs. In one example, each case may include afeedback indicator 1008 to allow for indicating (e.g., as feedback)whether the identification is indeed a violation (e.g., a validmisappropriation) or not a violation (e.g., a false positive).

FIG. 11 illustrates an example interface 1100 for displaying at least aportion of data analysis performed by a healthcare provider networkplatform. In an example, interface 1100 can be displayed when selectinga case from interface 1000. For example, interface 1100 displays alisting 1102 of dispensing event data, which may be determined to bepossible misappropriation of drugs for a healthcare professional orotherwise considered in making such a determination. The listing 1102can include a specific association of data determined to be possiblemisappropriation (e.g., the user performing the action a total of 10times in 15 minutes), along with more general information about theuser's usage of the electronic drug dispensing system 150 determined bydata analyzing component 128 from the drug dispensing data 152. Inaddition, for example, the more general information can includestatistical information regarding the user's usage and peer usage, etc.,which may be used to identify the user as an outlier of their peers (andthus suspect of misappropriating drugs). In this example, the interface1100 can display a listing of incidents 1104 determined for thehealthcare professional to allow for performing investigation of thehealthcare professional for possible misappropriation of drugs. Forexample, the listing of incidents 1104 may be of incidents detected fromthe drug dispensing data 152 that resulted in determining the possiblemisappropriation of drugs. Interface 1100 can also include caseinformation 1106 displaying information for updating case-specific data,such as a case type, healthcare professional role, etc.

FIG. 12 illustrates an example interface 1200 for displaying at leastanother portion of data analysis performed by a healthcare providernetwork platform. In an example, interface 1200 can be displayed whenselecting a case from interface 1000 or selecting incidents to view frominterface 1100. For example, interface 1200 displays a listing 1202 ofincidents for the healthcare professional suspected of misappropriatingdrugs, which may be determined to be possible misappropriation of drugsfor a healthcare professional or otherwise considered in making such adetermination. The listing 1202 can include listings of detectedincidents and related drug dispensing records for investigation. Inaddition, interface 1200 can include case information 1204 displayinginformation for updating case-specific data, such as a case type,healthcare professional role, etc.

FIG. 13 illustrates an example interface 1300 for displaying at leastanother portion of data analysis performed by a healthcare providernetwork platform. In an example, interface 1300 can be displayed whenselecting an incident from interface 1100 or 1200. For example,interface 1300 displays information 1302 of the healthcare professionalsuspected of misappropriating drugs. Interface 1300 also displays atimeline 1304 of accessing the electronic drug dispensing system 150 fordispensing drugs for a given patient, along with a triangular icon toindicate the dispensings or wastings that are part of the detectedincident. A listing 1306 of the dispensing or wasting events is alsodisplayed on the interface 1300. In addition, for a selected patient,corresponding EMR data 1308 can be displayed.

FIG. 14 illustrates an example interface 1400 for displaying at leastanother portion of data analysis performed by a healthcare providernetwork platform. In an example, interface 1400 can be displayed whenselecting to display medication events from interface 1100. For example,interface 1400 displays a listing 1402 of medication events performed bythe healthcare professional suspected of misappropriating drugs. Inaddition, interface 1400 can include case information 1404 displayinginformation for updating case-specific data, such as a case type,healthcare professional role, etc.

FIG. 15 illustrates an example system 1500 in accordance with aspectsdescribed herein. For example, system 1500 may include variousdistributed components as described in reference to the previousfigures. System 1500 may include, for example, a distributed analyticssystem 1502, which may perform one or more functions of the componentsdescribed herein (e.g., data receiving component 126, data analyzingcomponent 128, data presenting component 130, etc.). For example,distributed analytics system 1502 may receive data from a healthcare(HC) provider network platform 1504 (which may be similar to HC providernetwork platform 102 but having the various components distributed todistributed analytics system 1502). For example, HC provider networkplatform 1504 may include an agent 1506 that can operate without the HCprovider network platform 1504 for transferring data from one or morerepositories in the HC provider network platform 1504 (e.g., EMR data,EMR access data, HR data, drug dispensing data, etc., as described) todistributed analytics system 1502 for subsequent analysis. For example,agent 1506 may transfer the data to distributed analytics system 1502via secured hypertext transfer protocol (HTTPS) through one or morefirewalls.

In an example, distributed analytics system 1502 can include ananalytics and extract, transform, and load (ETL) component 1508 (whichmay be similar to and/or include at least a portion of data analyzingcomponent 128) that receives data from one or more filter components1510 (which may also be similar to and/or include at least a portion ofdata analyzing component 128). For example, the filter components 1510may apply whitelist filters, as described, to filter out EMR access datathat may be indicative of acceptable accesses of electronic patient data(e.g., legitimate authorized accesses, as described above), and theremaining EMR access data may be provided to the analytics and ETLcomponent 1508 for further analysis. In an example, distributedanalytics system 1502 may also include a product database 1512 that maystore data received from the one or more filter components 1510,analytics and ETL component 1508, etc., which may include data regardingpossible breaches or misappropriation of drugs, general EMR access data,etc., for alerting, viewing, etc. via a service layer 1514 and/orassociated user interface 1516.

For example, where analytics and ETL component 1508 detects a possiblebreach or misappropriation of drugs, as described above, the relatedinformation may be communicated to the product database 1512 and then toservice layer 1514 to alert an application (e.g., multi-factorapplication 1518) of the possible breach or misappropriation of drugs.Based on this alert, or otherwise, a compliance team 1520 (e.g., usingone or more devices) may access distributed analytics system 1502 viauser interface 1516 over HTTPS to view the possible breach and/orsubstantially any EMR access data (e.g., as shown in GUIs 400, 500, 600,700, 1000, 1100, 1200, 1300, 1400, and/or similar interfaces asdescribed herein). User interface 1516 may display the data based onaccessing product database 1512 via service layer 1514 to obtain thedata for display (e.g., based on one or more queries to the productdatabase 1512). In another example, a system management team 1522 (e.g.,using one or more devices) may access the distributed analytics system1502 (e.g., via an authenticator application 1524 and beacon server 1526architecture) to modify one or more components or related data (e.g.,rules, tags, metadata, etc.) of the distributed analytics system 1502.

Additionally, for example, system 1500 may include a distributed keymanagement component 1530 for managing one or more security keys used inaccessing data from distributed analytics system 1502. For example, thekeys can include one or more private keys, public keys, private/publickey pairs, etc. used to authenticate requests for data from distributedanalytics system 1502. Additionally, in an example, cloud storage 1532can be provided for at least a portion of the data in product database1512.

In some variations, aspects described herein may be directed toward oneor more computer systems capable of carrying out the functionalitydescribed herein. An example of such a computer system 1600 is shown inFIG. 16 .

Computer system 1600 may include one or more processors, such asprocessor 1604. The processor 1604 is connected to a communicationinfrastructure 1606 (e.g., a communications bus, cross-over bar, ornetwork). Various software aspects are described in terms of thisexample computer system. After reading this description, it will becomeapparent to a person skilled in the relevant art(s) how to implement thedescribed subject matter using other computer systems and/orarchitectures. For example, processor 1604 can implement the components126, 128, 130, 132, 134, 136, etc. described in connection with ahealthcare provider network platform 102 (FIG. 1 ), related methods 200,300, 900 and/or Blocks thereof (FIGS. 2, 3, 9 ), etc.

Computer system 1600 may include a display interface 1602 that forwardsgraphics, text, and other data from the communication infrastructure1606 (or from a frame buffer not shown) for display on a display unit1630. Computer system 1600 also includes a main memory 1608, preferablyrandom access memory (RAM), and may also include a secondary memory1610. The secondary memory 1610 may include, for example, a hard diskdrive 1612 and/or a removable storage drive 1614, representing a floppydisk drive, a magnetic tape drive, an optical disk drive, a flash memorydrive, etc. The removable storage drive 1614 reads from and/or writes toa removable storage unit 1618 in a well-known manner. Removable storageunit 1618, represents a floppy disk, magnetic tape, optical disk, flashmemory card, etc., which is read by and written to removable storagedrive 1614. As will be appreciated, the removable storage unit 1618includes a computer usable storage medium having stored therein computersoftware and/or data.

In alternative aspects, secondary memory 1610 may include other similardevices for allowing computer programs or other instructions to beloaded into computer system 1600. Such devices may include, for example,a removable storage unit 1622 and an interface 1620. Examples of suchmay include a program cartridge and cartridge interface (such as thatfound in video game devices), a removable memory chip (such as anerasable programmable read only memory (EPROM), or programmable readonly memory (PROM)) and associated socket, and other removable storageunits 1622 and interfaces 1620, which allow software and data to betransferred from the removable storage unit 1622 to computer system1600.

Computer system 1600 may also include a communications interface 1624.Communications interface 1624 allows software and data to be transferredbetween computer system 1600 and external devices. Examples ofcommunications interface 1624 may include a modem, a network interface(such as an Ethernet card), a communications port, a Personal ComputerMemory Card International Association (PCMCIA) slot and card, etc.Software and data transferred via communications interface 1624 are inthe form of signals 1628, which may be electronic, electromagnetic,optical or other signals capable of being received by communicationsinterface 1624. These signals 1628 are provided to communicationsinterface 1624 via a communications path (e.g., channel) 1626. This path1626 carries signals 1628 and may be implemented using wire or cable,fiber optics, a telephone line, a cellular link, a radio frequency (RF)link and/or other communications channels. In this document, the terms“computer program medium” and “computer usable medium” are used to refergenerally to media such as a removable storage drive 1614, a hard diskinstalled in hard disk drive 1612, and signals 1628. These computerprogram products provide software to the computer system 1600. Aspectsof the described subject matter may be directed to such computer programproducts.

Computer programs (also referred to as computer control logic) arestored in main memory 1608 and/or secondary memory 1610. Computerprograms may also be received via communications interface 1624. Suchcomputer programs, when executed, enable the computer system 1600 toperform the features of the subject matter described herein. Inparticular, the computer programs, when executed, enable the processor1604 to perform the features of the described subject matter.Accordingly, such computer programs represent controllers of thecomputer system 1600.

In an aspect where the aspects described herein are implemented usingsoftware, the software may be stored in a computer program product andloaded into computer system 1600 using removable storage drive 1614,hard disk drive 1612, or interface 1620. The control logic (software),when executed by the processor 1604, causes the processor 1604 toperform the functions of the subject matter described herein. In anotheraspect, the subject matter described herein may be implemented primarilyin hardware using, for example, hardware components, such as applicationspecific integrated circuits (ASICs). Implementation of the hardwarestate machine so as to perform the functions described herein will beapparent to persons skilled in the relevant art(s). In yet anotheraspect, variations of the described subject matter may be implementedusing a combination of both hardware and software.

In one example, display interface 1602 may provide interfaces related tothe healthcare provider network platform 102 (e.g., provided by datapresenting component 130, etc.) or related GUIs 400, 500, 600, 700,1000, 1100, 1200, 1300, 1400, and/or similar interfaces as describedherein. Interaction with these interfaces may be provided via inputdevices connected to communication infrastructure 1606, such as akeyboard, mouse, touch screen, voice input, and/or the like.

FIG. 17 shows a communication system 1700 involving use of variousfeatures in accordance with aspects described herein. The communicationsystem 1700 may include one or more assessors 1760, 1762 (also referredto interchangeably herein as one or more “users”, “entities,” etc.) andone or more terminals 1742, 1766 accessible by the one or more accessors1760, 1762. In one aspect, operations in accordance with aspectsdescribed herein may include, for example, input and/or accessed by anaccessor 1760 via terminal 1742, such as personal computers (PCs),minicomputers, mainframe computers, microcomputers, telephonic devices,or wireless devices, such as personal digital assistants (“PDAs”) or ahand-held wireless devices coupled to a remote device 1743, such as aserver, PC, minicomputer, mainframe computer, microcomputer, or otherdevice having a processor and a repository for data and/or connection toa repository for data, via, for example, a network 1744, such as theInternet or an intranet, and couplings 1745, 1764. The couplings 1745,1764 include, for example, wired, wireless, or fiberoptic links. Inanother aspect, the methods and systems described herein may operate ina stand-alone environment, such as on a single terminal.

While the foregoing has been described in conjunction with the exampleaspects outlined above and further described in the figures, variousalternatives, modifications, variations, improvements, and/orsubstantial equivalents, whether known or that are or may be presentlyunforeseen, may become apparent to those having at least ordinary skillin the art. Accordingly, the exemplary aspects, as set forth above, areintended to be illustrative, not limiting. Various changes may be madewithout departing from the spirit and scope of the subject matterdescribed herein. Therefore, aspects described herein intended toembrace all known or later-developed alternatives, modifications,variations, improvements, and/or substantial equivalents.

What is claimed is:
 1. A computer-implemented method for processing drug dispensing data to determine a possible drug misappropriation, the method comprising: receiving, by a drug diversion surveillance system, drug dispensing data from one or more dispensing logs, one or more electronic medical records, and human resources data; identifying, by the drug diversion surveillance system, a plurality of dispensing events by a plurality of employees based at least in part on the one or more dispensing logs; detecting, by the drug diversion surveillance system, at least one dispensing event based on the drug dispensing data that constitutes at least one drug misappropriation event by: determining whether the at least one dispensing event is inconsistent with one or more patterns including a drug wasting pattern; and in response to determining that the at least one dispensing event is inconsistent with the one or more patterns, identifying the at least one dispensing event as at least one drug misappropriation event; and transmitting, by a data analytics component of the drug diversion surveillance system, the at least one drug misappropriation event to a product database of the drug diversion surveillance system, wherein the product database transmits the at least one drug misappropriation event to a service layer of the drug diversion surveillance system to alert an application of a possible drug misappropriation.
 2. The computer-implemented method of claim 1, the method further comprising: storing, by the product database, misappropriation data received from the drug diversion surveillance system.
 3. The computer-implemented method of claim 1, wherein upon the at least one drug misappropriation event being transmitted to the product database, a distributed analytics system of the drug diversion surveillance system becomes accessible by one or more user devices to view the at least one drug misappropriation event.
 4. The computer-implemented method of claim 3, the method further comprising: managing, by a distributed key management component of the drug diversion surveillance system, one or more security keys to access the distributed analytics system, wherein the one or more security keys includes one or more private keys, one or more public keys, or one or more private/public key pairs.
 5. The computer-implemented method of claim 1, the detecting the at least one dispensing event based on the drug dispensing data that constitutes a drug misappropriation event further including: analyzing, by a data patterning component of the drug diversion surveillance system, the drug dispensing data to detect the one or more patterns; and determining, by the data patterning component, whether the at least one dispensing event of the plurality of dispensing events is inconsistent with the one or more pattern.
 6. The computer-implemented method of claim 5, the method further comprising: updating, by the data patterning component, the one or more patterns based on at least one change in the drug dispensing data or the human resources data.
 7. The computer-implemented method of claim 1, wherein each of the one or more dispensing logs includes one or more of: an employee requesting dispensing of a drug, patient information, the drug being dispensed, an amount of the drug being dispensed, or wasting information.
 8. The computer-implemented method of claim 1, wherein the human resources data includes employment information related to at least one employee of the plurality of employees and at least one security profile related to the at least one employee of the plurality of employees.
 9. The computer-implemented method of claim 1, the method further comprising: displaying, by one or more user interfaces, misappropriation data corresponding to the at least one drug misappropriation event, the displaying including retrieving the misappropriation data from the product database.
 10. A system for processing drug dispensing data to determine a possible drug misappropriation, the system comprising: at least one processor; and at least one storage comprising instructions which, when executed by the at least one processor, cause the at least one processor to perform operations comprising: receiving, by a drug diversion surveillance system, drug dispensing data from one or more dispensing logs, one or more electronic medical records, and human resources data; identifying, by the drug diversion surveillance system, a plurality of dispensing events by a plurality of employees based at least in part on the one or more dispensing logs; detecting, by the drug diversion surveillance system, at least one dispensing event based on the drug dispensing data that constitutes at least one drug misappropriation event by: determining whether the at least one dispensing event is inconsistent with one or more patterns including a drug wasting pattern; and in response to determining that the at least one dispensing event is inconsistent with the one or more patterns, identifying the at least one dispensing event as at least one drug misappropriation event; and transmitting, by a data analytics component of the drug diversion surveillance system, the at least one drug misappropriation event to a product database of the drug diversion surveillance system, wherein the product database transmits the at least one drug misappropriation event to a service layer of the drug diversion surveillance system to alert an application of a possible drug misappropriation.
 11. The system of claim 10, the operations further comprising: storing, by the product database, misappropriation data received from the drug diversion surveillance system.
 12. The system of claim 10, wherein upon the at least one drug misappropriation event being transmitted to the product database, a distributed analytics system of the drug diversion surveillance system becomes accessible by one or more user devices to view the at least one drug misappropriation event.
 13. The system of claim 10, the detecting the at least one dispensing event based on the drug dispensing data that constitutes a drug misappropriation event further including: analyzing, by a data patterning component of the drug diversion surveillance system, the drug dispensing data to detect the one or more patterns; and determining, by the data patterning component, whether the at least one dispensing event of the plurality of dispensing events is inconsistent with the one or more patterns.
 14. The system of claim 10, the operations further comprising: displaying, by one or more user interfaces, misappropriation data corresponding to the at least one drug misappropriation event, the displaying including retrieving the misappropriation data from the product database.
 15. A non-transitory computer readable medium storing instructions which, when executed by at least one processor, cause the at least one processor to perform operations for processing drug dispensing data to determine a possible drug misappropriation, the operations comprising: receiving, by a drug diversion surveillance system, drug dispensing data from one or more dispensing logs, one or more electronic medical records, and human resources data; identifying, by the drug diversion surveillance system, a plurality of dispensing events by a plurality of employees based at least in part on the one or more dispensing logs; detecting, by the drug diversion surveillance system, at least one dispensing event based on the drug dispensing data that constitutes at least one drug misappropriation event by: determining whether the at least one dispensing event is inconsistent with one or more patterns including a drug wasting pattern; and in response to determining that the at least one dispensing event is inconsistent with the one or more patterns, identifying the at least one dispensing event as at least one drug misappropriation event; and transmitting, by a data analytics component of the drug diversion surveillance system, the at least one drug misappropriation event to a product database of the drug diversion surveillance system, wherein the product database transmits the at least one drug misappropriation event to a service layer of the drug diversion surveillance system to alert an application of a possible drug misappropriation.
 16. The non-transitory computer readable medium of claim 15, the operations further comprising: storing, by the product database, misappropriation data received from the drug diversion surveillance system.
 17. The non-transitory computer readable medium of claim 15, wherein upon the at least one drug misappropriation event being transmitted to the product database, a distributed analytics system of the drug diversion surveillance system becomes accessible by one or more user devices to view the at least one drug misappropriation event.
 18. The non-transitory computer readable medium of claim 15, the detecting the at least one dispensing event based on the drug dispensing data that constitutes a drug misappropriation event further including: analyzing, by a data patterning component of the drug diversion surveillance system, the drug dispensing data to detect the one or more patterns; and determining, by the data patterning component, whether the at least one dispensing event of the plurality of dispensing events is inconsistent with the one or more patterns.
 19. The non-transitory computer readable medium of claim 15, the operations further comprising: displaying, by one or more user interfaces, misappropriation data corresponding to the at least one drug misappropriation event, the displaying including retrieving the misappropriation data from the product database.
 20. The non-transitory computer readable medium of claim 15, wherein each of the one or more dispensing logs includes one or more of: an employee requesting dispensing of a drug, patient information, the drug being dispensed, an amount of the drug being dispensed, or wasting information. 